Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44368f4d0369e9432c74a52c3aac683cf712491a2bbce2108b12ba3d063a3e88

Tx prefix hash: 9a4c1a8befb468b62dee411621daa1c6f30140845c23b2cdc38ad8a8fde92d2d
Tx public key: 4472a37fd5b4b113e67e396e0e26c171f631f72a35ba2d61a51d49f8018b9dac
Timestamp: 1728821640 Timestamp [UCT]: 2024-10-13 12:14:00 Age [y:d:h:m:s]: 00:185:06:01:20
Block: 1130693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132182 RingCT/type: yes/0
Extra: 014472a37fd5b4b113e67e396e0e26c171f631f72a35ba2d61a51d49f8018b9dac02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f81befe58025c19ee0a8cd2113b3ade18a3d21add88d5df6dd5dc8bd2480546d 0.600000000000 1613570 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": 1130703, "vin": [ { "gen": { "height": 1130693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f81befe58025c19ee0a8cd2113b3ade18a3d21add88d5df6dd5dc8bd2480546d" } } ], "extra": [ 1, 68, 114, 163, 127, 213, 180, 177, 19, 230, 126, 57, 110, 14, 38, 193, 113, 246, 49, 247, 42, 53, 186, 45, 97, 165, 29, 73, 248, 1, 139, 157, 172, 2, 17, 0, 0, 0, 2, 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