Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04cf918fbd32b02942dbb9607908d5c31559cf35557a77670cd7c213b7248a7f

Tx prefix hash: 126ad7181a5a52168dc0bdb6ac45932981d8708183a10a241ea2f377eba58875
Tx public key: 27843d1af89d1481a19d05a8f47a89e046c5b115666b9f7dc6322e9f8bd7cc03
Timestamp: 1638732816 Timestamp [UCT]: 2021-12-05 19:33:36 Age [y:d:h:m:s]: 03:099:03:24:49
Block: 389149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 849567 RingCT/type: yes/0
Extra: 0127843d1af89d1481a19d05a8f47a89e046c5b115666b9f7dc6322e9f8bd7cc030211000000141cab2639000000000000000000

1 output(s) for total of 31.521213564000 dcy

stealth address amount amount idx
00: 603ee495b82519523c792cb88ea51c6f892244c7dd0bd4bb9713f92566b3fa6c 31.521213564000 784176 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": 389159, "vin": [ { "gen": { "height": 389149 } } ], "vout": [ { "amount": 31521213564, "target": { "key": "603ee495b82519523c792cb88ea51c6f892244c7dd0bd4bb9713f92566b3fa6c" } } ], "extra": [ 1, 39, 132, 61, 26, 248, 157, 20, 129, 161, 157, 5, 168, 244, 122, 137, 224, 70, 197, 177, 21, 102, 107, 159, 125, 198, 50, 46, 159, 139, 215, 204, 3, 2, 17, 0, 0, 0, 20, 28, 171, 38, 57, 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