Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b27fb36ee7feb4cdc24d9efca4ae09494b2a081d4a0b7aad0580b571e73b5e2

Tx prefix hash: d325b79e82cffbdfbeaaec8b6c1fdaeefe92f0ce216abab405767de1855510ae
Tx public key: 1f115d57b5fe452c416adcdd7984930d1bf1e0adea38ea9fc381ac81e1112588
Timestamp: 1706622675 Timestamp [UCT]: 2024-01-30 13:51:15 Age [y:d:h:m:s]: 01:061:10:30:24
Block: 946631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304985 RingCT/type: yes/0
Extra: 011f115d57b5fe452c416adcdd7984930d1bf1e0adea38ea9fc381ac81e11125880211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be55487e86f7c0e33b0362dac0875d2b6ddf2a45b8dfb712a320a720a4ae98c1 0.600000000000 1404965 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": 946641, "vin": [ { "gen": { "height": 946631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be55487e86f7c0e33b0362dac0875d2b6ddf2a45b8dfb712a320a720a4ae98c1" } } ], "extra": [ 1, 31, 17, 93, 87, 181, 254, 69, 44, 65, 106, 220, 221, 121, 132, 147, 13, 27, 241, 224, 173, 234, 56, 234, 159, 195, 129, 172, 129, 225, 17, 37, 136, 2, 17, 0, 0, 0, 1, 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