Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80855a06924ff7aae6d8137755a3fdb1c94960cb1aaa2e21de1e0908204a8631

Tx prefix hash: decf082db52e69e40d3108d8f327da75cb13cb2199dfe6c9b61e8c0f02637e4e
Tx public key: 69f865a46bd2a027464b4fb736bd1788dc6bf4d8570af6f46656a42e54176606
Timestamp: 1697913043 Timestamp [UCT]: 2023-10-21 18:30:43 Age [y:d:h:m:s]: 02:064:01:44:33
Block: 874646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565450 RingCT/type: yes/0
Extra: 0169f865a46bd2a027464b4fb736bd1788dc6bf4d8570af6f46656a42e5417660602110000000533af99f4000000000000000000

1 output(s) for total of 0.776130481000 dcy

stealth address amount amount idx
00: fb72dd5449661f2e875280f512a91f6b9f4c45d0b2055cae46bf38870f9686a2 0.776130481000 1329868 of 0

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": 874656, "vin": [ { "gen": { "height": 874646 } } ], "vout": [ { "amount": 776130481, "target": { "key": "fb72dd5449661f2e875280f512a91f6b9f4c45d0b2055cae46bf38870f9686a2" } } ], "extra": [ 1, 105, 248, 101, 164, 107, 210, 160, 39, 70, 75, 79, 183, 54, 189, 23, 136, 220, 107, 244, 216, 87, 10, 246, 244, 102, 86, 164, 46, 84, 23, 102, 6, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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