Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac1cb2cfd8a9b7ac7f4eeb849d6808d3a422c1e1eccce71e73b3f1a707e0646a

Tx prefix hash: 605745b33ca89399b15eb5084db262c92ed120a8c7ea0b699cb23986ab4c6738
Tx public key: c557c9bedaa70be1191c96b4d95260a342f8d52aee409f974d3bbacdeeb5e527
Timestamp: 1715966510 Timestamp [UCT]: 2024-05-17 17:21:50 Age [y:d:h:m:s]: 00:340:10:28:16
Block: 1024120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243329 RingCT/type: yes/0
Extra: 01c557c9bedaa70be1191c96b4d95260a342f8d52aee409f974d3bbacdeeb5e527021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72c7185256d26dbf66c9a0935fbec2417f79b92db78bb525280c6f9e2894ca6d 0.600000000000 1489615 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": 1024130, "vin": [ { "gen": { "height": 1024120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72c7185256d26dbf66c9a0935fbec2417f79b92db78bb525280c6f9e2894ca6d" } } ], "extra": [ 1, 197, 87, 201, 190, 218, 167, 11, 225, 25, 28, 150, 180, 217, 82, 96, 163, 66, 248, 213, 42, 238, 64, 159, 151, 77, 59, 186, 205, 238, 181, 229, 39, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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