Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3f3efa918f9f8064a92169230530c6d4c267dcc837c0fbd3cd84487d6a2a7bb8

Tx prefix hash: 45d5df28a96d81b1b70ce29e016474a6b6456e3e043cbe7e2a66529c824b8082
Tx public key: 9a0e1ba5e5100fa5c91ffeb5ed80a9ca25a2678805e6e2cb8b9d510dc1d91c1d
Timestamp: 1714292600 Timestamp [UCT]: 2024-04-28 08:23:20 Age [y:d:h:m:s]: 01:192:13:46:35
Block: 1010230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396270 RingCT/type: yes/0
Extra: 019a0e1ba5e5100fa5c91ffeb5ed80a9ca25a2678805e6e2cb8b9d510dc1d91c1d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adfceafeac2ce90e8859047a9ce3a89001177d728cc7943bb1b3b585c24eb80c 0.600000000000 1472128 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1010240, "vin": [ { "gen": { "height": 1010230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adfceafeac2ce90e8859047a9ce3a89001177d728cc7943bb1b3b585c24eb80c" } } ], "extra": [ 1, 154, 14, 27, 165, 229, 16, 15, 165, 201, 31, 254, 181, 237, 128, 169, 202, 37, 162, 103, 136, 5, 230, 226, 203, 139, 157, 81, 13, 193, 217, 28, 29, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8