Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f133b42f311f64a11e734a1cdcd058f3ca9aa2cf268d339067bd08b754165170

Tx prefix hash: 646b74827477974be6dc36f6a40a531b4fb361873a0bf1fec1943022790fb226
Tx public key: ae7876a0b47589d2010f93483136a57b90667fa2c70a6d0ead52d031fb2d119c
Timestamp: 1698833473 Timestamp [UCT]: 2023-11-01 10:11:13 Age [y:d:h:m:s]: 02:052:22:09:06
Block: 882283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557460 RingCT/type: yes/0
Extra: 01ae7876a0b47589d2010f93483136a57b90667fa2c70a6d0ead52d031fb2d119c02110000000775e3f0e9000000000000000000

1 output(s) for total of 0.732200763000 dcy

stealth address amount amount idx
00: 07d3e80a72da575ef52b1912d79b6f163b2f35af2570ec826b6833984c7c4c08 0.732200763000 1337935 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": 882293, "vin": [ { "gen": { "height": 882283 } } ], "vout": [ { "amount": 732200763, "target": { "key": "07d3e80a72da575ef52b1912d79b6f163b2f35af2570ec826b6833984c7c4c08" } } ], "extra": [ 1, 174, 120, 118, 160, 180, 117, 137, 210, 1, 15, 147, 72, 49, 54, 165, 123, 144, 102, 127, 162, 199, 10, 109, 14, 173, 82, 208, 49, 251, 45, 17, 156, 2, 17, 0, 0, 0, 7, 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