Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83dbcaf64aeeb280d9d1daab944b42952712c8d4b088866b0d06c2de2e76b0b3

Tx prefix hash: 462550877d6fe5b4a6e2afe46825aef019f08b76fae5739f563b66856cdf6113
Tx public key: 0a6c17ae2a6336d819b5bf6bfdba1a111ac3e0b79e146fcc3049740ac4993dea
Timestamp: 1728733911 Timestamp [UCT]: 2024-10-12 11:51:51 Age [y:d:h:m:s]: 01:037:14:05:51
Block: 1129962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285246 RingCT/type: yes/0
Extra: 010a6c17ae2a6336d819b5bf6bfdba1a111ac3e0b79e146fcc3049740ac4993dea02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 798f682b3595314fbc2c16a767b1f712e5040417a625f03b016d65fb359bc460 0.600000000000 1612833 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": 1129972, "vin": [ { "gen": { "height": 1129962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "798f682b3595314fbc2c16a767b1f712e5040417a625f03b016d65fb359bc460" } } ], "extra": [ 1, 10, 108, 23, 174, 42, 99, 54, 216, 25, 181, 191, 107, 253, 186, 26, 17, 26, 195, 224, 183, 158, 20, 111, 204, 48, 73, 116, 10, 196, 153, 61, 234, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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