Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75af23c26d558697be3fcfc04d91de5a4a0adf4e69e459b451337160194236bc

Tx prefix hash: 4ef18f1add8585891c598f719976dfeeeeda54296ed51dcdc5303f2e9ac55c8f
Tx public key: 65972daebdca28797d0bfa4c3fb1be1b76ec4782bed4d8f6ee3feba92e986a41
Timestamp: 1722444378 Timestamp [UCT]: 2024-07-31 16:46:18 Age [y:d:h:m:s]: 01:069:01:56:47
Block: 1077818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307812 RingCT/type: yes/0
Extra: 0165972daebdca28797d0bfa4c3fb1be1b76ec4782bed4d8f6ee3feba92e986a4102110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb808c5cf839c77f4b52d857f2f563a7730475d9d55dfd14f3cf3b4bc15c4259 0.600000000000 1550373 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": 1077828, "vin": [ { "gen": { "height": 1077818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb808c5cf839c77f4b52d857f2f563a7730475d9d55dfd14f3cf3b4bc15c4259" } } ], "extra": [ 1, 101, 151, 45, 174, 189, 202, 40, 121, 125, 11, 250, 76, 63, 177, 190, 27, 118, 236, 71, 130, 190, 212, 216, 246, 238, 63, 235, 169, 46, 152, 106, 65, 2, 17, 0, 0, 0, 6, 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