Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e946be13368252aefa967a0aa93c8b6b2d093c449241899a73f7f33e6e1b198

Tx prefix hash: 811e71def49315920d26799cd17ea318c4da3eab0de918001dde19c695a74c8c
Tx public key: b76d668ea6be3ebf33427a4798415570a82b89bdbe5f63800b66ac47e2554f15
Timestamp: 1697937151 Timestamp [UCT]: 2023-10-22 01:12:31 Age [y:d:h:m:s]: 01:088:12:23:37
Block: 874844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324503 RingCT/type: yes/0
Extra: 01b76d668ea6be3ebf33427a4798415570a82b89bdbe5f63800b66ac47e2554f1502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.774958923000 dcy

stealth address amount amount idx
00: 3343f8e74384dd4d2c6b7428b2be4012e9c946206964660d3accc7e8d15cb64c 0.774958923000 1330076 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": 874854, "vin": [ { "gen": { "height": 874844 } } ], "vout": [ { "amount": 774958923, "target": { "key": "3343f8e74384dd4d2c6b7428b2be4012e9c946206964660d3accc7e8d15cb64c" } } ], "extra": [ 1, 183, 109, 102, 142, 166, 190, 62, 191, 51, 66, 122, 71, 152, 65, 85, 112, 168, 43, 137, 189, 190, 95, 99, 128, 11, 102, 172, 71, 226, 85, 79, 21, 2, 17, 0, 0, 0, 7, 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