Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379ac43443029054211ab7c3d5e23eeb22c59f73adc040cdc1df257416ae1eb2

Tx prefix hash: a2fe6841986f3e0afa0a729a24b4eddcc28eb0d88a13e4b8362d0d580ea473d7
Tx public key: e0b4650e6029d65bb67f36f51c5fa9dee094394d9ceedbe13482347721a11b81
Timestamp: 1720078523 Timestamp [UCT]: 2024-07-04 07:35:23 Age [y:d:h:m:s]: 00:276:06:13:33
Block: 1058202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197378 RingCT/type: yes/0
Extra: 01e0b4650e6029d65bb67f36f51c5fa9dee094394d9ceedbe13482347721a11b810211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9d799b876e34d286284b9e27e50e870af7ddd57a68d15456f787b102ed0f3e4 0.600000000000 1528651 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": 1058212, "vin": [ { "gen": { "height": 1058202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9d799b876e34d286284b9e27e50e870af7ddd57a68d15456f787b102ed0f3e4" } } ], "extra": [ 1, 224, 180, 101, 14, 96, 41, 214, 91, 182, 127, 54, 245, 28, 95, 169, 222, 224, 148, 57, 77, 156, 238, 219, 225, 52, 130, 52, 119, 33, 161, 27, 129, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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