Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6064f9df25079fda2add374ff88a10285079c3fa696d0af696da46647c3806f3

Tx prefix hash: a4a6728cc5fdf653f5afa1da2fe9dea346dda37524cf4dd2bbb7c94702e230d7
Tx public key: e9d53264add4e5a4edd0d8b2b03f76efb9a71d94234e0bfad32b8e38d3d8436f
Timestamp: 1634823290 Timestamp [UCT]: 2021-10-21 13:34:50 Age [y:d:h:m:s]: 03:068:22:44:05
Block: 357474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 827530 RingCT/type: yes/0
Extra: 01e9d53264add4e5a4edd0d8b2b03f76efb9a71d94234e0bfad32b8e38d3d8436f0211000000064a0f5013000000000000000000

1 output(s) for total of 40.136607006000 dcy

stealth address amount amount idx
00: d22ede0ff1583ca5f6ba8b60241278842268586f6b29c3411fbeec46f5844e53 40.136607006000 728912 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": 357484, "vin": [ { "gen": { "height": 357474 } } ], "vout": [ { "amount": 40136607006, "target": { "key": "d22ede0ff1583ca5f6ba8b60241278842268586f6b29c3411fbeec46f5844e53" } } ], "extra": [ 1, 233, 213, 50, 100, 173, 212, 229, 164, 237, 208, 216, 178, 176, 63, 118, 239, 185, 167, 29, 148, 35, 78, 11, 250, 211, 43, 142, 56, 211, 216, 67, 111, 2, 17, 0, 0, 0, 6, 74, 15, 80, 19, 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