Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23963ab7fbe0ac3769d07cffb230c5a60b7b28de3eb4d79e830a00c743a836ad

Tx prefix hash: b8262630cd292c4fc0048fef53d5a9fd2abe99842617c9f2d78cc67313859991
Tx public key: 98206d13b1e781d721c8cb2917212cbb68bb887417e0075a1eeee2f19fbde4e5
Timestamp: 1714838920 Timestamp [UCT]: 2024-05-04 16:08:40 Age [y:d:h:m:s]: 00:249:15:51:21
Block: 1014778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178685 RingCT/type: yes/0
Extra: 0198206d13b1e781d721c8cb2917212cbb68bb887417e0075a1eeee2f19fbde4e502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a30597f2dd650d28c5174db2732814ee0497a8aa69e52d72658ad1ff9e79e8b7 0.600000000000 1477961 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": 1014788, "vin": [ { "gen": { "height": 1014778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a30597f2dd650d28c5174db2732814ee0497a8aa69e52d72658ad1ff9e79e8b7" } } ], "extra": [ 1, 152, 32, 109, 19, 177, 231, 129, 215, 33, 200, 203, 41, 23, 33, 44, 187, 104, 187, 136, 116, 23, 224, 7, 90, 30, 238, 226, 241, 159, 189, 228, 229, 2, 17, 0, 0, 0, 2, 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