Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa14fb9ac8e7973bf2247e36d4f1cf615c2728c7ab062ff59e2a3ca6006d3a8

Tx prefix hash: a922838c24a501d48c2814194f7519370e433834cc7b635ee08ab6b19521d262
Tx public key: e4d5cea6bf11e45069b81e92e1db6a67813d0b53ccdf5898aa0a726e4724e887
Timestamp: 1721173261 Timestamp [UCT]: 2024-07-16 23:41:01 Age [y:d:h:m:s]: 00:268:03:22:31
Block: 1067296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191560 RingCT/type: yes/0
Extra: 01e4d5cea6bf11e45069b81e92e1db6a67813d0b53ccdf5898aa0a726e4724e88702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c24821f966e1de023d91837d870085a9e02da08a53e4ae3e611445b6f20c151 0.600000000000 1538073 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": 1067306, "vin": [ { "gen": { "height": 1067296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c24821f966e1de023d91837d870085a9e02da08a53e4ae3e611445b6f20c151" } } ], "extra": [ 1, 228, 213, 206, 166, 191, 17, 228, 80, 105, 184, 30, 146, 225, 219, 106, 103, 129, 61, 11, 83, 204, 223, 88, 152, 170, 10, 114, 110, 71, 36, 232, 135, 2, 17, 0, 0, 0, 4, 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