Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9be53e69c4f8d59c34772b33fb042d2fa7e3c6fe84cfbad45d0c5cd93f08067

Tx prefix hash: b4f48ad1bf0931224daba4b5da3eb0bc1323844ba84fc1fa801b0075af98807f
Tx public key: 1a473c7a72ea57e8c69b1caaf7a7a67b4c75d6b5aaac44f3f44f6ac63b8892b0
Timestamp: 1751407735 Timestamp [UCT]: 2025-07-01 22:08:55 Age [y:d:h:m:s]: 00:204:17:51:14
Block: 1316809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144500 RingCT/type: yes/0
Extra: 011a473c7a72ea57e8c69b1caaf7a7a67b4c75d6b5aaac44f3f44f6ac63b8892b0021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bf9471268105485d0a012d91d35bb6939af4e48937756d7d788943fa952a638 0.600000000000 1804472 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": 1316819, "vin": [ { "gen": { "height": 1316809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bf9471268105485d0a012d91d35bb6939af4e48937756d7d788943fa952a638" } } ], "extra": [ 1, 26, 71, 60, 122, 114, 234, 87, 232, 198, 155, 28, 170, 247, 167, 166, 123, 76, 117, 214, 181, 170, 172, 68, 243, 244, 79, 106, 198, 59, 136, 146, 176, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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