Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5524f540215f683a481c0ab626d591e6f46ac661f7cf9ef2a0f05b5cc06e4646

Tx prefix hash: b039084b800eef86fa18115c7e0c992b60005d7c2b5bf1ef9737ec7047370d5c
Tx public key: b3dfb0e8d13a8170e893cd86c8eed4e73eb8e8d31eb0cc1d4395db02a5d1c7a4
Timestamp: 1732311113 Timestamp [UCT]: 2024-11-22 21:31:53 Age [y:d:h:m:s]: 00:128:20:59:49
Block: 1159518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91925 RingCT/type: yes/0
Extra: 01b3dfb0e8d13a8170e893cd86c8eed4e73eb8e8d31eb0cc1d4395db02a5d1c7a4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3ef3e31a55269b821ca3da3fe4113f9799cbe3a518fc3d94724800ad40cc25 0.600000000000 1645155 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": 1159528, "vin": [ { "gen": { "height": 1159518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3ef3e31a55269b821ca3da3fe4113f9799cbe3a518fc3d94724800ad40cc25" } } ], "extra": [ 1, 179, 223, 176, 232, 209, 58, 129, 112, 232, 147, 205, 134, 200, 238, 212, 231, 62, 184, 232, 211, 30, 176, 204, 29, 67, 149, 219, 2, 165, 209, 199, 164, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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