Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5729c747949af7a141f8e02a569a1d518ff93c5adc11aa0cc41d39786e6616f5

Tx prefix hash: e700c6af71c827a51bcee8af11105a47e578808bd2d6baedb50c8e9175607e04
Tx public key: d52dab78c9af654a88aa32fe7b258e063f5d42b164858d28da243a3bf8e8e682
Timestamp: 1736963439 Timestamp [UCT]: 2025-01-15 17:50:39 Age [y:d:h:m:s]: 00:340:09:09:33
Block: 1198043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240824 RingCT/type: yes/0
Extra: 01d52dab78c9af654a88aa32fe7b258e063f5d42b164858d28da243a3bf8e8e6820211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c6b5914b54b0645a9f8cc9a77a30ba4c0fafc77f85eedc22c42536bb8e0b501 0.600000000000 1684660 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": 1198053, "vin": [ { "gen": { "height": 1198043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c6b5914b54b0645a9f8cc9a77a30ba4c0fafc77f85eedc22c42536bb8e0b501" } } ], "extra": [ 1, 213, 45, 171, 120, 201, 175, 101, 74, 136, 170, 50, 254, 123, 37, 142, 6, 63, 93, 66, 177, 100, 133, 141, 40, 218, 36, 58, 59, 248, 232, 230, 130, 2, 17, 0, 0, 0, 9, 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