Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c211647c6d35c746d120cf4a2e8f8397f1e8e8fdd286640120a891ea74d2617

Tx prefix hash: 8e801cc61a8a8c4ee1486dee279e36c2a623d4eabf96c700a991ab2ceed514ff
Tx public key: e97966e9974862305c14ea2194f809c90c539ed4b9957842411ea0853956e128
Timestamp: 1700483105 Timestamp [UCT]: 2023-11-20 12:25:05 Age [y:d:h:m:s]: 01:095:21:06:16
Block: 895757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329650 RingCT/type: yes/0
Extra: 01e97966e9974862305c14ea2194f809c90c539ed4b9957842411ea0853956e12802110000000875e3f0e9000000000000000000

1 output(s) for total of 0.660670936000 dcy

stealth address amount amount idx
00: f7f7d6091b16d2247964c5fb209ed05e83479570fd4ab4a5c1c3eedc9f2618f8 0.660670936000 1352004 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": 895767, "vin": [ { "gen": { "height": 895757 } } ], "vout": [ { "amount": 660670936, "target": { "key": "f7f7d6091b16d2247964c5fb209ed05e83479570fd4ab4a5c1c3eedc9f2618f8" } } ], "extra": [ 1, 233, 121, 102, 233, 151, 72, 98, 48, 92, 20, 234, 33, 148, 248, 9, 201, 12, 83, 158, 212, 185, 149, 120, 66, 65, 30, 160, 133, 57, 86, 225, 40, 2, 17, 0, 0, 0, 8, 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