Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4aab4438fee9cb533892b059f794028f2add06100ac4094e17e937663100404

Tx prefix hash: 78c31f6f9d1061183a4636e4dbef55f482a1bd5fe296aa49696b4e612a4a6d6c
Tx public key: e63116126d4b6a726bb0ca55b835cc55e8ecfbae703ae5be9e86562879bf2d0a
Timestamp: 1755278388 Timestamp [UCT]: 2025-08-15 17:19:48 Age [y:d:h:m:s]: 00:097:11:08:16
Block: 1347322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69378 RingCT/type: yes/0
Extra: 01e63116126d4b6a726bb0ca55b835cc55e8ecfbae703ae5be9e86562879bf2d0a0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b216ba0b0f2c8373ac798e08a2e73fa49a05c20d3f2cd451c2a36479125dd79f 0.600000000000 1835239 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": 1347332, "vin": [ { "gen": { "height": 1347322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b216ba0b0f2c8373ac798e08a2e73fa49a05c20d3f2cd451c2a36479125dd79f" } } ], "extra": [ 1, 230, 49, 22, 18, 109, 75, 106, 114, 107, 176, 202, 85, 184, 53, 204, 85, 232, 236, 251, 174, 112, 58, 229, 190, 158, 134, 86, 40, 121, 191, 45, 10, 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