Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f84613a0b2cd1a95818d04816a584ca8fa61fd8df3bba9fffffb7f2071640d

Tx prefix hash: 1664b316b77a435a134b5b321769ff57cd462cbf6aab1ab0cced3406f6eddd67
Tx public key: cf65d1ece8e259a8422b187c62e47ff04fa9bf807f8845eb90ec54aa149ddac8
Timestamp: 1700493943 Timestamp [UCT]: 2023-11-20 15:25:43 Age [y:d:h:m:s]: 01:137:04:42:42
Block: 895836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359229 RingCT/type: yes/0
Extra: 01cf65d1ece8e259a8422b187c62e47ff04fa9bf807f8845eb90ec54aa149ddac8021100000001679a8a81000000000000000000

1 output(s) for total of 0.660272854000 dcy

stealth address amount amount idx
00: 97e619979bb688b7a58d734b03e04f3ed9bd1ef7fcab2d3a70095463936e20f9 0.660272854000 1352083 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": 895846, "vin": [ { "gen": { "height": 895836 } } ], "vout": [ { "amount": 660272854, "target": { "key": "97e619979bb688b7a58d734b03e04f3ed9bd1ef7fcab2d3a70095463936e20f9" } } ], "extra": [ 1, 207, 101, 209, 236, 232, 226, 89, 168, 66, 43, 24, 124, 98, 228, 127, 240, 79, 169, 191, 128, 127, 136, 69, 235, 144, 236, 84, 170, 20, 157, 218, 200, 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