Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49a372e169139bbd5c5f4238c354fad876d688adbf8e519e9d1ee3241dfcdb8

Tx prefix hash: b998fe819a8567d4984843ca1441b70a6a1e43c3fee09f20901471cb5dc67e41
Tx public key: ae704258a12c3acc3b9ee81059e336de9e24da9867a71777b7c88b8dcea3d9fe
Timestamp: 1751580406 Timestamp [UCT]: 2025-07-03 22:06:46 Age [y:d:h:m:s]: 00:140:11:05:29
Block: 1318208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98634 RingCT/type: yes/0
Extra: 01ae704258a12c3acc3b9ee81059e336de9e24da9867a71777b7c88b8dcea3d9fe021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f7d3ee2903d82093acc6528bd61281948ee3f20f78b1dc2edbc35ba6564773 0.600000000000 1805885 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": 1318218, "vin": [ { "gen": { "height": 1318208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f7d3ee2903d82093acc6528bd61281948ee3f20f78b1dc2edbc35ba6564773" } } ], "extra": [ 1, 174, 112, 66, 88, 161, 44, 58, 204, 59, 158, 232, 16, 89, 227, 54, 222, 158, 36, 218, 152, 103, 167, 23, 119, 183, 200, 139, 141, 206, 163, 217, 254, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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