Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79b951678036832463cdfe219b6e36cb6f53a4dbb776f4696ac974863fef0afb

Tx prefix hash: 653005331935b9e3c0276a72877966fe0a0617316125c6ea443f94500e17f275
Tx public key: 000bba3b905b6a4a26e9b865ef974b1e28c4003a3a285f2b44db3deba4265b70
Timestamp: 1632306071 Timestamp [UCT]: 2021-09-22 10:21:11 Age [y:d:h:m:s]: 03:045:09:30:22
Block: 338727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 808579 RingCT/type: yes/0
Extra: 01000bba3b905b6a4a26e9b865ef974b1e28c4003a3a285f2b44db3deba4265b7002110000001afdc024ec000000000000000000

1 output(s) for total of 46.308932872000 dcy

stealth address amount amount idx
00: bfeccf456aaf90951e0fe0d5c0445b270b61916a791d16bb89d58160959917d2 46.308932872000 697004 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": 338737, "vin": [ { "gen": { "height": 338727 } } ], "vout": [ { "amount": 46308932872, "target": { "key": "bfeccf456aaf90951e0fe0d5c0445b270b61916a791d16bb89d58160959917d2" } } ], "extra": [ 1, 0, 11, 186, 59, 144, 91, 106, 74, 38, 233, 184, 101, 239, 151, 75, 30, 40, 196, 0, 58, 58, 40, 95, 43, 68, 219, 61, 235, 164, 38, 91, 112, 2, 17, 0, 0, 0, 26, 253, 192, 36, 236, 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