Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3bed7a2b173e9bead6c7677d1a409b36710f1859c52eaee52f2979dce23c5e

Tx prefix hash: 2e15a51349200a24afcf8217634fc09aa07bc55e83312c3510848c1a6b2bb46f
Tx public key: ac4edcf9cbe29f99ebe9fbf64ea336c0d939fc712e1cfa88450f62696c9a30cf
Timestamp: 1722185338 Timestamp [UCT]: 2024-07-28 16:48:58 Age [y:d:h:m:s]: 01:103:11:04:09
Block: 1075672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332434 RingCT/type: yes/0
Extra: 01ac4edcf9cbe29f99ebe9fbf64ea336c0d939fc712e1cfa88450f62696c9a30cf02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73c1c6ceaac697c98d1999fc63b5966251853e9dccfd59f8e15e4f45f5efa6b2 0.600000000000 1548201 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": 1075682, "vin": [ { "gen": { "height": 1075672 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73c1c6ceaac697c98d1999fc63b5966251853e9dccfd59f8e15e4f45f5efa6b2" } } ], "extra": [ 1, 172, 78, 220, 249, 203, 226, 159, 153, 235, 233, 251, 246, 78, 163, 54, 192, 217, 57, 252, 113, 46, 28, 250, 136, 69, 15, 98, 105, 108, 154, 48, 207, 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