Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a55a98bab36cd49864e28f61ff4180add976589967b378a29c1fd649641337

Tx prefix hash: bac80589d5ca0a026a4a37937c17ad0d3a73c89cb2f01f1c82fba07f4942b733
Tx public key: cb1f25cdc982bf4d8d695e1e6c83e6330144e9bb696b74c3d411f9316b6ff434
Timestamp: 1710710352 Timestamp [UCT]: 2024-03-17 21:19:12 Age [y:d:h:m:s]: 00:221:21:04:51
Block: 980559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158877 RingCT/type: yes/0
Extra: 01cb1f25cdc982bf4d8d695e1e6c83e6330144e9bb696b74c3d411f9316b6ff434021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 376f23680afb296e5d48a628252033c9a03b4b77ffd78eeb1d00abf8b2f646b9 0.600000000000 1440634 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": 980569, "vin": [ { "gen": { "height": 980559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "376f23680afb296e5d48a628252033c9a03b4b77ffd78eeb1d00abf8b2f646b9" } } ], "extra": [ 1, 203, 31, 37, 205, 201, 130, 191, 77, 141, 105, 94, 30, 108, 131, 230, 51, 1, 68, 233, 187, 105, 107, 116, 195, 212, 17, 249, 49, 107, 111, 244, 52, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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