Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 053831ac29551b5152ba37e30689160dcff7cd8b2eff376ee4c5b75ec312c0fe

Tx prefix hash: 683d13772544510a079f02ee741ac9359efb292c85067501ba664768e1245f1c
Tx public key: 141bcdf7144c50d294b27ddd460aff2a2d1f8f5ea72992cae01a77063f1eeb43
Timestamp: 1737520490 Timestamp [UCT]: 2025-01-22 04:34:50 Age [y:d:h:m:s]: 00:293:12:05:03
Block: 1202615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207302 RingCT/type: yes/0
Extra: 01141bcdf7144c50d294b27ddd460aff2a2d1f8f5ea72992cae01a77063f1eeb430211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01a0ecfced3305e080b7b9a6d22307cd3866b8e0e12bbc8765b2d09edbdc3f91 0.600000000000 1689280 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": 1202625, "vin": [ { "gen": { "height": 1202615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01a0ecfced3305e080b7b9a6d22307cd3866b8e0e12bbc8765b2d09edbdc3f91" } } ], "extra": [ 1, 20, 27, 205, 247, 20, 76, 80, 210, 148, 178, 125, 221, 70, 10, 255, 42, 45, 31, 143, 94, 167, 41, 146, 202, 224, 26, 119, 6, 63, 30, 235, 67, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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