Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b291c2a23ab700c326751ddb58794d50e607e08c86def97b2f82a96675e440

Tx prefix hash: c1cd4c896987cc9d3d3f957f4c0ba18496a763a054070ce6261ba97a6dfa0a5f
Tx public key: bb6293aa9e6881a6a152d096c5d7e09f220fa3a3636a9a79368c746404a2a546
Timestamp: 1736280691 Timestamp [UCT]: 2025-01-07 20:11:31 Age [y:d:h:m:s]: 00:083:19:54:12
Block: 1192395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59679 RingCT/type: yes/0
Extra: 01bb6293aa9e6881a6a152d096c5d7e09f220fa3a3636a9a79368c746404a2a546021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abd5a391ba791e2063e1789cf99dc42520e1f32479955503ae58deccbe9bf59a 0.600000000000 1678946 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": 1192405, "vin": [ { "gen": { "height": 1192395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abd5a391ba791e2063e1789cf99dc42520e1f32479955503ae58deccbe9bf59a" } } ], "extra": [ 1, 187, 98, 147, 170, 158, 104, 129, 166, 161, 82, 208, 150, 197, 215, 224, 159, 34, 15, 163, 163, 99, 106, 154, 121, 54, 140, 116, 100, 4, 162, 165, 70, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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