Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cf436d709f146c6eb95c4971525d88ecf0acc77c2f060cb2cf206f2c6d0399

Tx prefix hash: f1d5d49b9cf911ef5e3c7d83bc1a00438351f633a6ad82c3c900b6963cc50586
Tx public key: 50db5c16f8ed7b56a233b34f9235337fbb4b554f1e6d70f9009fdd926e6f3b37
Timestamp: 1734367821 Timestamp [UCT]: 2024-12-16 16:50:21 Age [y:d:h:m:s]: 00:024:06:25:06
Block: 1176581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17341 RingCT/type: yes/0
Extra: 0150db5c16f8ed7b56a233b34f9235337fbb4b554f1e6d70f9009fdd926e6f3b37021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a05caec96a9f7bdbf5616031943ba08fc8981ed23eb0ba81815abef8d84aa9b 0.600000000000 1662934 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": 1176591, "vin": [ { "gen": { "height": 1176581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a05caec96a9f7bdbf5616031943ba08fc8981ed23eb0ba81815abef8d84aa9b" } } ], "extra": [ 1, 80, 219, 92, 22, 248, 237, 123, 86, 162, 51, 179, 79, 146, 53, 51, 127, 187, 75, 85, 79, 30, 109, 112, 249, 0, 159, 221, 146, 110, 111, 59, 55, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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