Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4023524001294ec26672c9482c246e10db85ae3fc26d1d22226943624ef23985

Tx prefix hash: aa8c2f1a5cfc12c7a7766d406166f7b64a20bd52df94079ed13980bf8ca7f3a1
Tx public key: 2ab4b60ba20ecbcf49c97476225040037a2d868e5fda84c99c0ea0f6f0a8bdea
Timestamp: 1722926366 Timestamp [UCT]: 2024-08-06 06:39:26 Age [y:d:h:m:s]: 00:223:05:54:03
Block: 1081809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159462 RingCT/type: yes/0
Extra: 012ab4b60ba20ecbcf49c97476225040037a2d868e5fda84c99c0ea0f6f0a8bdea021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 377bb8417ab044219546dc5eaef68a36ae6e52aba983977210b8a5259c3c5005 0.600000000000 1555632 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": 1081819, "vin": [ { "gen": { "height": 1081809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "377bb8417ab044219546dc5eaef68a36ae6e52aba983977210b8a5259c3c5005" } } ], "extra": [ 1, 42, 180, 182, 11, 162, 14, 203, 207, 73, 201, 116, 118, 34, 80, 64, 3, 122, 45, 134, 142, 95, 218, 132, 201, 156, 14, 160, 246, 240, 168, 189, 234, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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