Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4bdd2d82c6be8aa771429c28d9a0877b9433ddb0f53a97576344bdf4c42459c

Tx prefix hash: bf7e0083230b3aebc1396a5d730664577f76db570ace580198185a448dfc51e8
Tx public key: 38fea48b87b13f360987749ea18bb2a5fc3bf606682d8c026c5098182242f2b8
Timestamp: 1744692994 Timestamp [UCT]: 2025-04-15 04:56:34 Age [y:d:h:m:s]: 00:029:17:15:25
Block: 1261765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21272 RingCT/type: yes/0
Extra: 0138fea48b87b13f360987749ea18bb2a5fc3bf606682d8c026c5098182242f2b8021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4b53ebd20eba3bcf5c0a2d5cb4e65f0211a838c7336e70ba91b9124045f3fe5 0.600000000000 1748940 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": 1261775, "vin": [ { "gen": { "height": 1261765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4b53ebd20eba3bcf5c0a2d5cb4e65f0211a838c7336e70ba91b9124045f3fe5" } } ], "extra": [ 1, 56, 254, 164, 139, 135, 177, 63, 54, 9, 135, 116, 158, 161, 139, 178, 165, 252, 59, 246, 6, 104, 45, 140, 2, 108, 80, 152, 24, 34, 66, 242, 184, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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