Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f5ef8e517647fe20531af2129e9cb6659db4dc14644afee63a921a1b8be927

Tx prefix hash: af2406e3d811b7929cdaf3d9940168e253da15d9134e9c5e7f8ff0429e57a2ce
Tx public key: 0945714c03a4e4e3725df8db6acb4a67b70fc0ae3fc49259a9d1de5e7f4ec0a9
Timestamp: 1750208596 Timestamp [UCT]: 2025-06-18 01:03:16 Age [y:d:h:m:s]: 00:155:18:19:14
Block: 1307306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109135 RingCT/type: yes/0
Extra: 010945714c03a4e4e3725df8db6acb4a67b70fc0ae3fc49259a9d1de5e7f4ec0a9021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8994099c26b5162ca862b8b477b16c2ef0ae00ee8fdaa8dd4226d0756110d87d 0.600000000000 1794917 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": 1307316, "vin": [ { "gen": { "height": 1307306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8994099c26b5162ca862b8b477b16c2ef0ae00ee8fdaa8dd4226d0756110d87d" } } ], "extra": [ 1, 9, 69, 113, 76, 3, 164, 228, 227, 114, 93, 248, 219, 106, 203, 74, 103, 183, 15, 192, 174, 63, 196, 146, 89, 169, 209, 222, 94, 127, 78, 192, 169, 2, 17, 0, 0, 0, 1, 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