Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8979a364e63bfa076fbdc17374b8dd005c5d6ebd234b2dea9db39a56ca120ae

Tx prefix hash: 8f4118262e39797b19ce53baecb0382e8344ce9e374295f19b4ce3bfc1350b35
Tx public key: 001d0d8fb4575876ff4abf70ffb2735944479af8bbc882853777f1f4ec34f1b8
Timestamp: 1699701857 Timestamp [UCT]: 2023-11-11 11:24:17 Age [y:d:h:m:s]: 01:126:17:38:17
Block: 889281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351762 RingCT/type: yes/0
Extra: 01001d0d8fb4575876ff4abf70ffb2735944479af8bbc882853777f1f4ec34f1b8021100000001679a8a81000000000000000000

1 output(s) for total of 0.694133314000 dcy

stealth address amount amount idx
00: 1215ec11b653824e5cbb28fad77e7b2b3f3f4846226418b8ce92c835985e1d66 0.694133314000 1345264 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": 889291, "vin": [ { "gen": { "height": 889281 } } ], "vout": [ { "amount": 694133314, "target": { "key": "1215ec11b653824e5cbb28fad77e7b2b3f3f4846226418b8ce92c835985e1d66" } } ], "extra": [ 1, 0, 29, 13, 143, 180, 87, 88, 118, 255, 74, 191, 112, 255, 178, 115, 89, 68, 71, 154, 248, 187, 200, 130, 133, 55, 119, 241, 244, 236, 52, 241, 184, 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