Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d634cc988c4a444bb2c745c5eaa4dc7d7a9a4137014b46b8ba579c9ae6a168

Tx prefix hash: dd459fa4e23c4770fa2c62afc56e7d990e6dce37bea17574b153ba993957f612
Tx public key: d4c4111cc5e0bd9cfb9ee2846a97fc5ef9fe9c0f7231241138e49ed7471196c3
Timestamp: 1708883555 Timestamp [UCT]: 2024-02-25 17:52:35 Age [y:d:h:m:s]: 01:080:17:24:55
Block: 965399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318723 RingCT/type: yes/0
Extra: 01d4c4111cc5e0bd9cfb9ee2846a97fc5ef9fe9c0f7231241138e49ed7471196c30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8594e549605b4398efdb16e23ab6b44508a601bd8d670c2c96785c638bb6a54 0.600000000000 1425150 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": 965409, "vin": [ { "gen": { "height": 965399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8594e549605b4398efdb16e23ab6b44508a601bd8d670c2c96785c638bb6a54" } } ], "extra": [ 1, 212, 196, 17, 28, 197, 224, 189, 156, 251, 158, 226, 132, 106, 151, 252, 94, 249, 254, 156, 15, 114, 49, 36, 17, 56, 228, 158, 215, 71, 17, 150, 195, 2, 17, 0, 0, 0, 2, 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