Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf3728f70aa7ff8c19ea0305416fc0264411af3e0549ad96b338d4c3b6c36e18

Tx prefix hash: d56fba39f8741cf323ae9eae55948db59af14613004046b0646f5958e7525d10
Tx public key: d241acd9595682977a3808de09ecda77fda937863a57c4f0bc045c3bbc01b1b3
Timestamp: 1582385291 Timestamp [UCT]: 2020-02-22 15:28:11 Age [y:d:h:m:s]: 05:253:03:19:54
Block: 70264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331852 RingCT/type: yes/0
Extra: 01d241acd9595682977a3808de09ecda77fda937863a57c4f0bc045c3bbc01b1b30211000000068a2ee0d9000000000000000000

1 output(s) for total of 359.082706498000 dcy

stealth address amount amount idx
00: d795b3cb4d5de225b0321de19017fa7fd1735c59a55e71698b44245aecdf65d3 359.082706498000 129773 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": 70274, "vin": [ { "gen": { "height": 70264 } } ], "vout": [ { "amount": 359082706498, "target": { "key": "d795b3cb4d5de225b0321de19017fa7fd1735c59a55e71698b44245aecdf65d3" } } ], "extra": [ 1, 210, 65, 172, 217, 89, 86, 130, 151, 122, 56, 8, 222, 9, 236, 218, 119, 253, 169, 55, 134, 58, 87, 196, 240, 188, 4, 92, 59, 188, 1, 177, 179, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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