Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3164e1f4b416ea7f7c1c13ccca8cb1eeb5eeb7be8ff205f8a356ef24ebc7fd8b

Tx prefix hash: c10dfcd4f986b87e7d6339ca88bce429b03f38ec884cc3eeea33e8d7b24fbd1d
Tx public key: 47707f16097e5851b3c7397c9112ca8367fb3418c9527579ed4413de28ce7a62
Timestamp: 1663511550 Timestamp [UCT]: 2022-09-18 14:32:30 Age [y:d:h:m:s]: 03:043:21:11:30
Block: 590656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 811251 RingCT/type: yes/0
Extra: 0147707f16097e5851b3c7397c9112ca8367fb3418c9527579ed4413de28ce7a62021100000002e6d27f9c000000000000000000

1 output(s) for total of 6.775035146000 dcy

stealth address amount amount idx
00: 70a14ebd6233879e0287cfbb4cbb76ca96b3af204764dace4ee666b8188e13ee 6.775035146000 1025095 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": 590666, "vin": [ { "gen": { "height": 590656 } } ], "vout": [ { "amount": 6775035146, "target": { "key": "70a14ebd6233879e0287cfbb4cbb76ca96b3af204764dace4ee666b8188e13ee" } } ], "extra": [ 1, 71, 112, 127, 22, 9, 126, 88, 81, 179, 199, 57, 124, 145, 18, 202, 131, 103, 251, 52, 24, 201, 82, 117, 121, 237, 68, 19, 222, 40, 206, 122, 98, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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