Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fd45fa08e902152ee607bcbe611bbb83912951d951080f481c47031a2ca3339

Tx prefix hash: 1220be4f4331b5273ed62cbbcccb76c91aedb9f82b740f9d6cc324380856c4a8
Tx public key: 957600ad326a6fc9fdabdf160ba90e6cc29a776f31719ab094ede19c5ad6b3c7
Timestamp: 1658842464 Timestamp [UCT]: 2022-07-26 13:34:24 Age [y:d:h:m:s]: 02:237:10:02:58
Block: 552160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690877 RingCT/type: yes/0
Extra: 01957600ad326a6fc9fdabdf160ba90e6cc29a776f31719ab094ede19c5ad6b3c7021100000001ec6d1a1a000000000000000000

1 output(s) for total of 9.087927141000 dcy

stealth address amount amount idx
00: fbb2dd92f33515a40a6bd714ed2f1593c7b3b38603c9d6398e311023c4d9f086 9.087927141000 983830 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": 552170, "vin": [ { "gen": { "height": 552160 } } ], "vout": [ { "amount": 9087927141, "target": { "key": "fbb2dd92f33515a40a6bd714ed2f1593c7b3b38603c9d6398e311023c4d9f086" } } ], "extra": [ 1, 149, 118, 0, 173, 50, 106, 111, 201, 253, 171, 223, 22, 11, 169, 14, 108, 194, 154, 119, 111, 49, 113, 154, 176, 148, 237, 225, 156, 90, 214, 179, 199, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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