Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8006348414a670cfe34d65d485edd674569fec86fa74c041caf6d445057364ac

Tx prefix hash: 2d07bd4b9e54733ae22e495506044d47c718501aeca5ac633917cb1cc34c4a52
Tx public key: 1111ded7cb51a3e1def5a76584de2c5e204e37a18e5a5202e3a4ce3e3365d86d
Timestamp: 1727715572 Timestamp [UCT]: 2024-09-30 16:59:32 Age [y:d:h:m:s]: 00:184:10:40:07
Block: 1121530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131602 RingCT/type: yes/0
Extra: 011111ded7cb51a3e1def5a76584de2c5e204e37a18e5a5202e3a4ce3e3365d86d02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d94510729e6c2c3a224e87e51e4409e4e7d7848dfeba8c33de69fb58125bcf1 0.600000000000 1603819 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": 1121540, "vin": [ { "gen": { "height": 1121530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d94510729e6c2c3a224e87e51e4409e4e7d7848dfeba8c33de69fb58125bcf1" } } ], "extra": [ 1, 17, 17, 222, 215, 203, 81, 163, 225, 222, 245, 167, 101, 132, 222, 44, 94, 32, 78, 55, 161, 142, 90, 82, 2, 227, 164, 206, 62, 51, 101, 216, 109, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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