Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cdb954ec673e475f96f5a990e5407b6f519b68cf382fc1b1c6f32bed327ef26

Tx prefix hash: 613234cf35e89881392c34352527f29e0b489ebfe17c69ac8645a5fcb61ed500
Tx public key: 3905a6df57532b6a0cb45234970fb5420a99503365dad4d4d3c7730559585b91
Timestamp: 1695481253 Timestamp [UCT]: 2023-09-23 15:00:53 Age [y:d:h:m:s]: 01:121:10:10:04
Block: 854480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348034 RingCT/type: yes/0
Extra: 013905a6df57532b6a0cb45234970fb5420a99503365dad4d4d3c7730559585b91021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.905257828000 dcy

stealth address amount amount idx
00: ea60060eae0ad1e8b85eb466aeddefa04a7163ba534bab1c0818273a6a46e036 0.905257828000 1308454 of 0

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": 854490, "vin": [ { "gen": { "height": 854480 } } ], "vout": [ { "amount": 905257828, "target": { "key": "ea60060eae0ad1e8b85eb466aeddefa04a7163ba534bab1c0818273a6a46e036" } } ], "extra": [ 1, 57, 5, 166, 223, 87, 83, 43, 106, 12, 180, 82, 52, 151, 15, 181, 66, 10, 153, 80, 51, 101, 218, 212, 212, 211, 199, 115, 5, 89, 88, 91, 145, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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