Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848df0ba2533245b1f0611aa70093e3a2b6c9af0ca7143670cb638c3ce599f16

Tx prefix hash: 6ffdee332c94981a7381445759afcabe84446652a250621ced621eec9ae8a4e0
Tx public key: 8a472dadf0e9fcc6ebe7ea82f8e26bcbea5aa026d8fa089a7c4375094c882092
Timestamp: 1721252983 Timestamp [UCT]: 2024-07-17 21:49:43 Age [y:d:h:m:s]: 00:256:16:54:18
Block: 1067958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183367 RingCT/type: yes/0
Extra: 018a472dadf0e9fcc6ebe7ea82f8e26bcbea5aa026d8fa089a7c4375094c88209202110000001a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2eb76811a7e97b7f0e48274ee7be28e021528d77277a0aecb63e5700bf8af91 0.600000000000 1538915 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": 1067968, "vin": [ { "gen": { "height": 1067958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2eb76811a7e97b7f0e48274ee7be28e021528d77277a0aecb63e5700bf8af91" } } ], "extra": [ 1, 138, 71, 45, 173, 240, 233, 252, 198, 235, 231, 234, 130, 248, 226, 107, 203, 234, 90, 160, 38, 216, 250, 8, 154, 124, 67, 117, 9, 76, 136, 32, 146, 2, 17, 0, 0, 0, 26, 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