Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 465ba42cb57976f1d20e9de2b83b56b290328ad48479c000b08208aa4ba6d988

Tx prefix hash: cd2322543e220dc6c64f87314379d818002543e2db4136b0093e5e9d9367f759
Tx public key: bd7327e553ec78b951e74b3dc3aeaff581115442dfd394fa9cfe30d0c36ae2f0
Timestamp: 1685366187 Timestamp [UCT]: 2023-05-29 13:16:27 Age [y:d:h:m:s]: 01:335:23:51:27
Block: 770678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501362 RingCT/type: yes/0
Extra: 01bd7327e553ec78b951e74b3dc3aeaff581115442dfd394fa9cfe30d0c36ae2f002110000000175e3f0e9000000000000000000

1 output(s) for total of 1.715631593000 dcy

stealth address amount amount idx
00: 1d86bb12315301fdff6b87062463cbfec64f04d707338bae60d6c4a98c9b56d6 1.715631593000 1220007 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": 770688, "vin": [ { "gen": { "height": 770678 } } ], "vout": [ { "amount": 1715631593, "target": { "key": "1d86bb12315301fdff6b87062463cbfec64f04d707338bae60d6c4a98c9b56d6" } } ], "extra": [ 1, 189, 115, 39, 229, 83, 236, 120, 185, 81, 231, 75, 61, 195, 174, 175, 245, 129, 17, 84, 66, 223, 211, 148, 250, 156, 254, 48, 208, 195, 106, 226, 240, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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