Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e3ba4e3f4a7c9d69e45a0f0ede0c50ed4a0bbad222a63051a19635c4f0b5058

Tx prefix hash: 3063e29e8df62feffcf9c0c4767abb3dccc6bcbc9aadaf47addd5fccd571e9d0
Tx public key: 3ea2dc5186be187418f8c8d12af784471db0f9482fdc97f07918cb3b7cb8b344
Timestamp: 1632412826 Timestamp [UCT]: 2021-09-23 16:00:26 Age [y:d:h:m:s]: 04:039:04:23:46
Block: 339537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1062632 RingCT/type: yes/0
Extra: 013ea2dc5186be187418f8c8d12af784471db0f9482fdc97f07918cb3b7cb8b3440211000000163fc41461000000000000000000

1 output(s) for total of 46.022838781000 dcy

stealth address amount amount idx
00: 038708464d3c67c51d0c23da6e02053295210e9e904e9e244f778707224bd96b 46.022838781000 698280 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": 339547, "vin": [ { "gen": { "height": 339537 } } ], "vout": [ { "amount": 46022838781, "target": { "key": "038708464d3c67c51d0c23da6e02053295210e9e904e9e244f778707224bd96b" } } ], "extra": [ 1, 62, 162, 220, 81, 134, 190, 24, 116, 24, 248, 200, 209, 42, 247, 132, 71, 29, 176, 249, 72, 47, 220, 151, 240, 121, 24, 203, 59, 124, 184, 179, 68, 2, 17, 0, 0, 0, 22, 63, 196, 20, 97, 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