Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ea4237e23e0b16890883902103c117da868647d3116f09d8f7780389c23c6c

Tx prefix hash: 34fca1213dd3d2da5c40de0a9ba3084a7e50530b77f12f4eece2288cc2a4bda1
Tx public key: 2b6e74eac1e72d9edda551c644e7c21fa40bb8bcf83e5711fac9a3a61570aac1
Timestamp: 1712985955 Timestamp [UCT]: 2024-04-13 05:25:55 Age [y:d:h:m:s]: 00:318:18:45:08
Block: 999383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227897 RingCT/type: yes/0
Extra: 012b6e74eac1e72d9edda551c644e7c21fa40bb8bcf83e5711fac9a3a61570aac102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6ce9cc0a4c4367cb79c834a651ef49281e47130e809aa7efc21f1e377dfeb1b 0.600000000000 1459861 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": 999393, "vin": [ { "gen": { "height": 999383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6ce9cc0a4c4367cb79c834a651ef49281e47130e809aa7efc21f1e377dfeb1b" } } ], "extra": [ 1, 43, 110, 116, 234, 193, 231, 45, 158, 221, 165, 81, 198, 68, 231, 194, 31, 164, 11, 184, 188, 248, 62, 87, 17, 250, 201, 163, 166, 21, 112, 170, 193, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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