Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c9996ed580f054ffae4519dc18c7d95e1009e75085fad9beafee5e78995db1

Tx prefix hash: 4da65dc3f27ef5e3bd0117c64115e661afff24b24b3d1153123cc11a8de8003e
Tx public key: 9a14df49c20a43d61d1f101a9797a45db4237798dea274e3e2e0c2712681b185
Timestamp: 1730429322 Timestamp [UCT]: 2024-11-01 02:48:42 Age [y:d:h:m:s]: 00:142:16:35:29
Block: 1143941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101806 RingCT/type: yes/0
Extra: 019a14df49c20a43d61d1f101a9797a45db4237798dea274e3e2e0c2712681b185021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4f4f93ba0a9d554d640a30ba0461eaf66102a513b7b38acfaf01d4bf7e9188 0.600000000000 1627980 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": 1143951, "vin": [ { "gen": { "height": 1143941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4f4f93ba0a9d554d640a30ba0461eaf66102a513b7b38acfaf01d4bf7e9188" } } ], "extra": [ 1, 154, 20, 223, 73, 194, 10, 67, 214, 29, 31, 16, 26, 151, 151, 164, 93, 180, 35, 119, 152, 222, 162, 116, 227, 226, 224, 194, 113, 38, 129, 177, 133, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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