Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddff5e7bbd48f5df8ec26c496142d10d16e7e40b8595b9b495452b2b372aaf92

Tx prefix hash: 44976aad29366d8d92ba2a4d885d717f4925c8d441e931f223812fdbed48cb34
Tx public key: b08b4a0cd51aaa861a817f9f0b11e60e598a9c6cbc5410f6523a58acf6a94ac4
Timestamp: 1755958931 Timestamp [UCT]: 2025-08-23 14:22:11 Age [y:d:h:m:s]: 00:035:04:46:44
Block: 1352745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25019 RingCT/type: yes/0
Extra: 01b08b4a0cd51aaa861a817f9f0b11e60e598a9c6cbc5410f6523a58acf6a94ac40211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72926ce361db63eea105744a55079bd803eb8615edd8a39a506c8346ba9026d4 0.600000000000 1840712 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": 1352755, "vin": [ { "gen": { "height": 1352745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72926ce361db63eea105744a55079bd803eb8615edd8a39a506c8346ba9026d4" } } ], "extra": [ 1, 176, 139, 74, 12, 213, 26, 170, 134, 26, 129, 127, 159, 11, 17, 230, 14, 89, 138, 156, 108, 188, 84, 16, 246, 82, 58, 88, 172, 246, 169, 74, 196, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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