Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 852ec93317fe3bfb44110fcb4da6e45202622af806fbf68d75e1f0deea50c792

Tx prefix hash: b39516049186308ebf8866f3a4d1fbc02c443b315cf94da13aeb5c4579637de8
Tx public key: 53ad8ddc46e98b504ab8a38b2f20de4595523770825bf93e36e5bbf83958c5b6
Timestamp: 1577172781 Timestamp [UCT]: 2019-12-24 07:33:01 Age [y:d:h:m:s]: 05:045:08:26:57
Block: 30489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182257 RingCT/type: yes/0
Extra: 0153ad8ddc46e98b504ab8a38b2f20de4595523770825bf93e36e5bbf83958c5b60211000000824fb58672000000000000000000

1 output(s) for total of 486.382732179000 dcy

stealth address amount amount idx
00: 97a9d5f14ec6291b3fbe7deda02a7b18026adb8f884239a17c63338a3a3c464b 486.382732179000 50341 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": 30499, "vin": [ { "gen": { "height": 30489 } } ], "vout": [ { "amount": 486382732179, "target": { "key": "97a9d5f14ec6291b3fbe7deda02a7b18026adb8f884239a17c63338a3a3c464b" } } ], "extra": [ 1, 83, 173, 141, 220, 70, 233, 139, 80, 74, 184, 163, 139, 47, 32, 222, 69, 149, 82, 55, 112, 130, 91, 249, 62, 54, 229, 187, 248, 57, 88, 197, 182, 2, 17, 0, 0, 0, 130, 79, 181, 134, 114, 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