Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199e4360a66b5d3ae642bf03543a002a1d4c146607b8b211f5d927fc27eb3756

Tx prefix hash: fb58bdbfa2d2c70b5b446a2de67730be47f6fa0b81e5758833edafc55d03c43f
Tx public key: 4f3aa6a59d8f6ef4866fc687831b411355451b09dc3e7efa52235c8d303b2589
Timestamp: 1721263347 Timestamp [UCT]: 2024-07-18 00:42:27 Age [y:d:h:m:s]: 00:266:10:05:39
Block: 1068047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190320 RingCT/type: yes/0
Extra: 014f3aa6a59d8f6ef4866fc687831b411355451b09dc3e7efa52235c8d303b258902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9698a2a017571c28f83cca89179d41b6ee5d6a3d7e8d669ba856464d900b77 0.600000000000 1539036 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": 1068057, "vin": [ { "gen": { "height": 1068047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9698a2a017571c28f83cca89179d41b6ee5d6a3d7e8d669ba856464d900b77" } } ], "extra": [ 1, 79, 58, 166, 165, 157, 143, 110, 244, 134, 111, 198, 135, 131, 27, 65, 19, 85, 69, 27, 9, 220, 62, 126, 250, 82, 35, 92, 141, 48, 59, 37, 137, 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