Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e71f3962e0b1a1e6588fc4b9f32058b51d22a4c74cc9251533ab33e85862f04

Tx prefix hash: e106b1d9add600707a4e6a0d64c9f99fa0a8c549384a80f747d1a51a00ef6e01
Tx public key: a834e827dd2bc252abaa893ad32e6d81eeb8ee957af1d9f2c4e21a6d6c24d4b0
Timestamp: 1719179404 Timestamp [UCT]: 2024-06-23 21:50:04 Age [y:d:h:m:s]: 00:201:06:49:03
Block: 1050744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144046 RingCT/type: yes/0
Extra: 01a834e827dd2bc252abaa893ad32e6d81eeb8ee957af1d9f2c4e21a6d6c24d4b00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8a6d489e113a9e2a1900aaa819113e7ec4799b1e72996b4deaee2bfc9a9726e 0.600000000000 1520919 of 15

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": 1050754, "vin": [ { "gen": { "height": 1050744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8a6d489e113a9e2a1900aaa819113e7ec4799b1e72996b4deaee2bfc9a9726e" } } ], "extra": [ 1, 168, 52, 232, 39, 221, 43, 194, 82, 171, 170, 137, 58, 211, 46, 109, 129, 238, 184, 238, 149, 122, 241, 217, 242, 196, 226, 26, 109, 108, 36, 212, 176, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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