Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70d2e6671c5f7c00cc9607bce09ad9c54e3a835dcd4e2a5af16e9fcb57931bb9

Tx prefix hash: 80920a97fa998f8e90efd880523d42e6d6f6c0e9d827a732d371188a20d2f578
Tx public key: 6e26aad897ea67bd134ddca093153921d3d67a25f86575cbe2829b15d37ddedc
Timestamp: 1751006151 Timestamp [UCT]: 2025-06-27 06:35:51 Age [y:d:h:m:s]: 00:190:01:20:06
Block: 1313693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133922 RingCT/type: yes/0
Extra: 016e26aad897ea67bd134ddca093153921d3d67a25f86575cbe2829b15d37ddedc02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b6d5b41fcde1a4f9b4a677cde19619aa8060860a483816ad088df1d2f9e3cb1 0.600000000000 1801334 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": 1313703, "vin": [ { "gen": { "height": 1313693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b6d5b41fcde1a4f9b4a677cde19619aa8060860a483816ad088df1d2f9e3cb1" } } ], "extra": [ 1, 110, 38, 170, 216, 151, 234, 103, 189, 19, 77, 220, 160, 147, 21, 57, 33, 211, 214, 122, 37, 248, 101, 117, 203, 226, 130, 155, 21, 211, 125, 222, 220, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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