Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9162f0a7fec8efde5af90a3720e43773701a2534b4bea3b532204ac1c84ee965

Tx prefix hash: 875a5a4153f1f826e0ac1a4ed7845dc64389124473dce6fa78cd06280a9451c6
Tx public key: bb46c636019fd5f0176b8b5f009159a6f40a2d2e8d0e75964f67d81e4740157d
Timestamp: 1761075876 Timestamp [UCT]: 2025-10-21 19:44:36 Age [y:d:h:m:s]: 00:078:23:58:30
Block: 1394986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56565 RingCT/type: yes/0
Extra: 01bb46c636019fd5f0176b8b5f009159a6f40a2d2e8d0e75964f67d81e4740157d02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198455dcfe0edc5777c875d221e315f65669cd98921ef3a244ba580b0aa717bc 0.600000000000 1883261 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": 1394996, "vin": [ { "gen": { "height": 1394986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198455dcfe0edc5777c875d221e315f65669cd98921ef3a244ba580b0aa717bc" } } ], "extra": [ 1, 187, 70, 198, 54, 1, 159, 213, 240, 23, 107, 139, 95, 0, 145, 89, 166, 244, 10, 45, 46, 141, 14, 117, 150, 79, 103, 216, 30, 71, 64, 21, 125, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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