Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d3ce1173edd54873318f16e4bb2f4786632f31e57be1b9bc044f934ae8252a5

Tx prefix hash: 2a7362d7e7925e8d44f15f0f53404b4e54318cde019f99d0f0bee8509ab5bd93
Tx public key: d3335de3f8571535721905de71f70f68cb202d8e34f29f5a6e82cc92adcaa804
Timestamp: 1755335023 Timestamp [UCT]: 2025-08-16 09:03:43 Age [y:d:h:m:s]: 00:049:16:01:50
Block: 1347753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35203 RingCT/type: yes/0
Extra: 01d3335de3f8571535721905de71f70f68cb202d8e34f29f5a6e82cc92adcaa804021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b3017a7c3fb82f08d39f8782426529106040e97f41b48f2d431cdabcb1ebf1 0.600000000000 1835674 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": 1347763, "vin": [ { "gen": { "height": 1347753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b3017a7c3fb82f08d39f8782426529106040e97f41b48f2d431cdabcb1ebf1" } } ], "extra": [ 1, 211, 51, 93, 227, 248, 87, 21, 53, 114, 25, 5, 222, 113, 247, 15, 104, 203, 32, 45, 142, 52, 242, 159, 90, 110, 130, 204, 146, 173, 202, 168, 4, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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