Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1fe30bc15e62a76b15abb37653c1ebf0b57c76e6fd1dd434ffdf315fdbb660

Tx prefix hash: ccbbee3154b866ead6c1d64625b530bb5d0cb901c02485b2210d2fc5ff9625ac
Tx public key: 0ff0354e64879f5e9f891a2195b7e3861e30e4853e1730e3386872ddc4f9c61f
Timestamp: 1755981989 Timestamp [UCT]: 2025-08-23 20:46:29 Age [y:d:h:m:s]: 00:087:10:31:24
Block: 1352940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62429 RingCT/type: yes/0
Extra: 010ff0354e64879f5e9f891a2195b7e3861e30e4853e1730e3386872ddc4f9c61f0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 075bd53fa75a4154ff4bc4ef69077ea1fa03e24aa09ec2c98f289a09c6fd9cbf 0.600000000000 1840909 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": 1352950, "vin": [ { "gen": { "height": 1352940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "075bd53fa75a4154ff4bc4ef69077ea1fa03e24aa09ec2c98f289a09c6fd9cbf" } } ], "extra": [ 1, 15, 240, 53, 78, 100, 135, 159, 94, 159, 137, 26, 33, 149, 183, 227, 134, 30, 48, 228, 133, 62, 23, 48, 227, 56, 104, 114, 221, 196, 249, 198, 31, 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