Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2a9c3a89da26a4880f9380186eafd471c5bfb7126aff2f9bd3f298b343c9a5

Tx prefix hash: d4d9224d8657f4cc7d6ef6e04868f881f74779ca7b8892d00fddb05fefc03dd0
Tx public key: df746468ef56790728080381d91bf64ec6229cbe3b5299a753e640d8cfd65b7f
Timestamp: 1580888634 Timestamp [UCT]: 2020-02-05 07:43:54 Age [y:d:h:m:s]: 05:098:15:18:20
Block: 59058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1222557 RingCT/type: yes/0
Extra: 01df746468ef56790728080381d91bf64ec6229cbe3b5299a753e640d8cfd65b7f02110000000149b77a3d000000000000000000

1 output(s) for total of 391.126417018000 dcy

stealth address amount amount idx
00: 1d8cc3267a53216174f59a72d716e6f8f84976750e330274e7043ecf118c921b 391.126417018000 109047 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": 59068, "vin": [ { "gen": { "height": 59058 } } ], "vout": [ { "amount": 391126417018, "target": { "key": "1d8cc3267a53216174f59a72d716e6f8f84976750e330274e7043ecf118c921b" } } ], "extra": [ 1, 223, 116, 100, 104, 239, 86, 121, 7, 40, 8, 3, 129, 217, 27, 246, 78, 198, 34, 156, 190, 59, 82, 153, 167, 83, 230, 64, 216, 207, 214, 91, 127, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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