Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbabed276d475b464f7b65aa8582e02831338f6efe1425e23c09195d711a2e75

Tx prefix hash: 61bada8d06d0f90f4bd6cac92e1c41f13b9d00d6a85f8c82969af82a1078ee5b
Tx public key: e92211a608957163e0260233d60d48174e1203e98e57b7fb2adf8c9a24f47041
Timestamp: 1743830006 Timestamp [UCT]: 2025-04-05 05:13:26 Age [y:d:h:m:s]: 00:278:11:44:46
Block: 1254614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196850 RingCT/type: yes/0
Extra: 01e92211a608957163e0260233d60d48174e1203e98e57b7fb2adf8c9a24f470410211000000044060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7e60dd5bac31cc8fed1c1ab0b46f61807d0d9ccb71f19ad2ed54bd2076eabc 0.600000000000 1741695 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": 1254624, "vin": [ { "gen": { "height": 1254614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7e60dd5bac31cc8fed1c1ab0b46f61807d0d9ccb71f19ad2ed54bd2076eabc" } } ], "extra": [ 1, 233, 34, 17, 166, 8, 149, 113, 99, 224, 38, 2, 51, 214, 13, 72, 23, 78, 18, 3, 233, 142, 87, 183, 251, 42, 223, 140, 154, 36, 244, 112, 65, 2, 17, 0, 0, 0, 4, 64, 96, 246, 210, 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