Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1965be5808c6e62f1ded439ebf323b04d17a3f5564b75275080dcff725885bfb

Tx prefix hash: 1add37abd5221d0d30ab8c7c9ad7555f670d2b43fe3830ea8c4bb1a0905b7148
Tx public key: 9d95ade077990d65a0c96b26b7fb1a85614ed9c7fa9dff2af862d3186720a993
Timestamp: 1741144070 Timestamp [UCT]: 2025-03-05 03:07:50 Age [y:d:h:m:s]: 00:260:05:14:51
Block: 1232391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183723 RingCT/type: yes/0
Extra: 019d95ade077990d65a0c96b26b7fb1a85614ed9c7fa9dff2af862d3186720a9930211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f30f202c899ec34f9f8f451ea3ede7eed33065362f9ec75cf98ef92c616fddc 0.600000000000 1719304 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": 1232401, "vin": [ { "gen": { "height": 1232391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f30f202c899ec34f9f8f451ea3ede7eed33065362f9ec75cf98ef92c616fddc" } } ], "extra": [ 1, 157, 149, 173, 224, 119, 153, 13, 101, 160, 201, 107, 38, 183, 251, 26, 133, 97, 78, 217, 199, 250, 157, 255, 42, 248, 98, 211, 24, 103, 32, 169, 147, 2, 17, 0, 0, 0, 2, 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