Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f59611c784df8347b7d89c1b3d850bb17e633ce350d5def2755f775e95f07c

Tx prefix hash: 364ca4da5fea6ef22075653fb412dbed0b83594afed230f093c8324dce7fec96
Tx public key: 7e6e62fa3eec8a47a44d12e922fc9a6e12577b9681adb604fa7fabc5d626e17c
Timestamp: 1699397418 Timestamp [UCT]: 2023-11-07 22:50:18 Age [y:d:h:m:s]: 01:187:13:54:42
Block: 886758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395267 RingCT/type: yes/0
Extra: 017e6e62fa3eec8a47a44d12e922fc9a6e12577b9681adb604fa7fabc5d626e17c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.707624137000 dcy

stealth address amount amount idx
00: 01a3d05bdf2ea5a6d2de8a5de8830269eacd95db19bee17ea5fc2e7b44b2c738 0.707624137000 1342601 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": 886768, "vin": [ { "gen": { "height": 886758 } } ], "vout": [ { "amount": 707624137, "target": { "key": "01a3d05bdf2ea5a6d2de8a5de8830269eacd95db19bee17ea5fc2e7b44b2c738" } } ], "extra": [ 1, 126, 110, 98, 250, 62, 236, 138, 71, 164, 77, 18, 233, 34, 252, 154, 110, 18, 87, 123, 150, 129, 173, 182, 4, 250, 127, 171, 197, 214, 38, 225, 124, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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