Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e71c36041652d32cff7888b9f19eeb7e96ae975457f725e574a3ee03dc8cd2

Tx prefix hash: ab22125f4fe69da44176fd83a4eb267da4ea2ecddf526dd1e69e4e6af4141e62
Tx public key: 9f9ba8df2a66d2751520ce01f1e5f9fa7e51d2fa8da48bf90101c2d77ddb6331
Timestamp: 1751471376 Timestamp [UCT]: 2025-07-02 15:49:36 Age [y:d:h:m:s]: 00:130:06:14:51
Block: 1317316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91341 RingCT/type: yes/0
Extra: 019f9ba8df2a66d2751520ce01f1e5f9fa7e51d2fa8da48bf90101c2d77ddb6331021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee367432913ce7c8c8334f2e7a07efb56773873627dcf374463bce1e6feb71ad 0.600000000000 1804983 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": 1317326, "vin": [ { "gen": { "height": 1317316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee367432913ce7c8c8334f2e7a07efb56773873627dcf374463bce1e6feb71ad" } } ], "extra": [ 1, 159, 155, 168, 223, 42, 102, 210, 117, 21, 32, 206, 1, 241, 229, 249, 250, 126, 81, 210, 250, 141, 164, 139, 249, 1, 1, 194, 215, 125, 219, 99, 49, 2, 17, 0, 0, 0, 2, 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