Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09108e63a6d1bb00822fccd1f16c4d0f3450ab28c0dfda633b44eb42990b85c

Tx prefix hash: 4245ef7451da7f1a79a11a7d9a24b89bc0e9b0477f7820458dc3dc4a8008cf34
Tx public key: 9cac6ecfc2741c8992695bc046bd009c468aac4925abab4a505d77280065a42f
Timestamp: 1697385851 Timestamp [UCT]: 2023-10-15 16:04:11 Age [y:d:h:m:s]: 01:097:00:50:01
Block: 870280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330558 RingCT/type: yes/0
Extra: 019cac6ecfc2741c8992695bc046bd009c468aac4925abab4a505d77280065a42f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.802418839000 dcy

stealth address amount amount idx
00: 6f6f42b0045c940f41a2c6adc423206b915f878eebd4c7186bea13bac2e407b1 0.802418839000 1325159 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": 870290, "vin": [ { "gen": { "height": 870280 } } ], "vout": [ { "amount": 802418839, "target": { "key": "6f6f42b0045c940f41a2c6adc423206b915f878eebd4c7186bea13bac2e407b1" } } ], "extra": [ 1, 156, 172, 110, 207, 194, 116, 28, 137, 146, 105, 91, 192, 70, 189, 0, 156, 70, 138, 172, 73, 37, 171, 171, 74, 80, 93, 119, 40, 0, 101, 164, 47, 2, 17, 0, 0, 0, 1, 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