Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd9305fed98ed25f5614ca49d6bf37b9f288352f5a1d1397298f12319749ce68

Tx prefix hash: e0d8485ebb6b0a301ae2f2cbca041a4532cf5861c71976aaee47738219b9b308
Tx public key: dddb0786e369e4f934f4a64c9d7d2c7d9b93eddb9c8aff4d642df3430c745d40
Timestamp: 1719857923 Timestamp [UCT]: 2024-07-01 18:18:43 Age [y:d:h:m:s]: 00:355:07:20:44
Block: 1056369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253759 RingCT/type: yes/0
Extra: 01dddb0786e369e4f934f4a64c9d7d2c7d9b93eddb9c8aff4d642df3430c745d400211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2c78a3564b190049fc3181ca08e4f7d41432eeec045123d3774da78e615c35 0.600000000000 1526782 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": 1056379, "vin": [ { "gen": { "height": 1056369 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2c78a3564b190049fc3181ca08e4f7d41432eeec045123d3774da78e615c35" } } ], "extra": [ 1, 221, 219, 7, 134, 227, 105, 228, 249, 52, 244, 166, 76, 157, 125, 44, 125, 155, 147, 237, 219, 156, 138, 255, 77, 100, 45, 243, 67, 12, 116, 93, 64, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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