Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80e5b161f4d4091c6ebe44c1180c9895d42c014d75ce6df38c7f436a174fb5b8

Tx prefix hash: 4723904b38c5001c3f7c916f5827b2469d62f38673640c2df334e98c88527e70
Tx public key: e79817cace107ca6f9f60ba70c4e3089b5a255d2cb0c9a68968434b3741d65fa
Timestamp: 1697419123 Timestamp [UCT]: 2023-10-16 01:18:43 Age [y:d:h:m:s]: 02:030:08:00:13
Block: 870551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541300 RingCT/type: yes/0
Extra: 01e79817cace107ca6f9f60ba70c4e3089b5a255d2cb0c9a68968434b3741d65fa02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.800761493000 dcy

stealth address amount amount idx
00: d56697b501a31b0f5fbaa2936fd1570c5bb4eb69d3d11b360c8065b60c7fe507 0.800761493000 1325434 of 0

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": 870561, "vin": [ { "gen": { "height": 870551 } } ], "vout": [ { "amount": 800761493, "target": { "key": "d56697b501a31b0f5fbaa2936fd1570c5bb4eb69d3d11b360c8065b60c7fe507" } } ], "extra": [ 1, 231, 152, 23, 202, 206, 16, 124, 166, 249, 246, 11, 167, 12, 78, 48, 137, 181, 162, 85, 210, 203, 12, 154, 104, 150, 132, 52, 179, 116, 29, 101, 250, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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