Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ac9f675e72068f830c9fd47ed6eaddbf4fb9b7156cfce1a8a356c93bee66c24

Tx prefix hash: 12c6c68b88c6a3871d7a0cc831864de1ef22eb09f1b2ee4664f9259433a611b9
Tx public key: 369c6e02dd92389f10c90eb512c5a68d1512b87078b5e6a95a50b0ce5048ebb2
Timestamp: 1721158373 Timestamp [UCT]: 2024-07-16 19:32:53 Age [y:d:h:m:s]: 00:131:07:17:23
Block: 1067172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93942 RingCT/type: yes/0
Extra: 01369c6e02dd92389f10c90eb512c5a68d1512b87078b5e6a95a50b0ce5048ebb202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f9ad240c5de0ee0da38db613ed928f134f35f3723994657bac35438e5cbe0d 0.600000000000 1537911 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": 1067182, "vin": [ { "gen": { "height": 1067172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f9ad240c5de0ee0da38db613ed928f134f35f3723994657bac35438e5cbe0d" } } ], "extra": [ 1, 54, 156, 110, 2, 221, 146, 56, 159, 16, 201, 14, 181, 18, 197, 166, 141, 21, 18, 184, 112, 120, 181, 230, 169, 90, 80, 176, 206, 80, 72, 235, 178, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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