Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d82289cc545f1db7bd93328a4260d146f54084a1157a4e35cfb16ec7b9a4e3b1

Tx prefix hash: 41d66b8bfd3cc5286c64ee00163745507584354295a06702b08dcc848acbe8da
Tx public key: cdd910bfe7dd8fe46a136062923e8f67b65919e27fd2fdf3142065d613ce91e5
Timestamp: 1721391959 Timestamp [UCT]: 2024-07-19 12:25:59 Age [y:d:h:m:s]: 00:257:11:01:35
Block: 1069111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183897 RingCT/type: yes/0
Extra: 01cdd910bfe7dd8fe46a136062923e8f67b65919e27fd2fdf3142065d613ce91e502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65bd3580bb15c0c852aa6ff38735e13c0e5b1d442b13e4c5e4a5952c1e479a6b 0.600000000000 1540406 of 15

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": 1069121, "vin": [ { "gen": { "height": 1069111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65bd3580bb15c0c852aa6ff38735e13c0e5b1d442b13e4c5e4a5952c1e479a6b" } } ], "extra": [ 1, 205, 217, 16, 191, 231, 221, 143, 228, 106, 19, 96, 98, 146, 62, 143, 103, 182, 89, 25, 226, 127, 210, 253, 243, 20, 32, 101, 214, 19, 206, 145, 229, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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