Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a382c1f8ada81ec7195e1f857e3c9e67eac38f9e4b174f6cbf91b3b96efdbc

Tx prefix hash: 6e7dc08ba63a11fb2069a80628ac31f14e5c660b3dfee7f080d1a75039d63ef2
Tx public key: 7bb96f10c7763abbb81a41bd12f20aa15e56ce2fdb2b61d054fbe928c93517e5
Timestamp: 1703853167 Timestamp [UCT]: 2023-12-29 12:32:47 Age [y:d:h:m:s]: 01:017:10:27:19
Block: 923688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273795 RingCT/type: yes/0
Extra: 017bb96f10c7763abbb81a41bd12f20aa15e56ce2fdb2b61d054fbe928c93517e502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e23b218a7ed206c7e6032a9279ae9d63d99665a43a3b2d72b72c820428cfcedc 0.600000000000 1381422 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": 923698, "vin": [ { "gen": { "height": 923688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e23b218a7ed206c7e6032a9279ae9d63d99665a43a3b2d72b72c820428cfcedc" } } ], "extra": [ 1, 123, 185, 111, 16, 199, 118, 58, 187, 184, 26, 65, 189, 18, 242, 10, 161, 94, 86, 206, 47, 219, 43, 97, 208, 84, 251, 233, 40, 201, 53, 23, 229, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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