Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3df4a9f7614419d96378e4fc66cf84f47aa588b82f26b7d20e3e44ebce7833f

Tx prefix hash: 44320dc9e3686f84d757b4d7587fe8c61143ae287042d2cdce808d3a0d0f6e9e
Tx public key: c794d2095384ab75e4d0b351e5a18113b8b47030182da7dd22ae56c128b3e618
Timestamp: 1720169516 Timestamp [UCT]: 2024-07-05 08:51:56 Age [y:d:h:m:s]: 00:263:22:32:19
Block: 1058956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188566 RingCT/type: yes/0
Extra: 01c794d2095384ab75e4d0b351e5a18113b8b47030182da7dd22ae56c128b3e61802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05065ce83cdd6022f6a0196565d772c60fe6359d5969b076f1061ac26f5f6bf0 0.600000000000 1529415 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": 1058966, "vin": [ { "gen": { "height": 1058956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05065ce83cdd6022f6a0196565d772c60fe6359d5969b076f1061ac26f5f6bf0" } } ], "extra": [ 1, 199, 148, 210, 9, 83, 132, 171, 117, 228, 208, 179, 81, 229, 161, 129, 19, 184, 180, 112, 48, 24, 45, 167, 221, 34, 174, 86, 193, 40, 179, 230, 24, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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