Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c067f3a56715ccf31445b906e932bb824a61e31a063dd42c3741ebad614189c9

Tx prefix hash: 45862290e241f89604e902853e50e647c71f02e7304b6d417ee904ba3b9b7282
Tx public key: 539546e8dc6e4b10e4fa9974a8334368a7f3f2b804117ea095cc7cb8117ff9a1
Timestamp: 1701127412 Timestamp [UCT]: 2023-11-27 23:23:32 Age [y:d:h:m:s]: 01:167:16:03:59
Block: 901097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381010 RingCT/type: yes/0
Extra: 01539546e8dc6e4b10e4fa9974a8334368a7f3f2b804117ea095cc7cb8117ff9a10211000000034b8f5122000000000000000000

1 output(s) for total of 0.634295394000 dcy

stealth address amount amount idx
00: 9a38b3262f5d1fa228caee5b3c6f7f1dd6d33d58bb106886cc0c233d061d5ed8 0.634295394000 1357628 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": 901107, "vin": [ { "gen": { "height": 901097 } } ], "vout": [ { "amount": 634295394, "target": { "key": "9a38b3262f5d1fa228caee5b3c6f7f1dd6d33d58bb106886cc0c233d061d5ed8" } } ], "extra": [ 1, 83, 149, 70, 232, 220, 110, 75, 16, 228, 250, 153, 116, 168, 51, 67, 104, 167, 243, 242, 184, 4, 17, 126, 160, 149, 204, 124, 184, 17, 127, 249, 161, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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