Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdae71348cdd768c422878ec192bfa78427137273478695b1c5668ce79a09f0

Tx prefix hash: 55d4d221d3a33bc0c5e3d246ce29bdf43ea4865b94689303d059f094b4bb37a2
Tx public key: ec63d8ee6e8b54ec611722a0c5ec48f3146f5380f8bc40e0414134a6a49b6636
Timestamp: 1731907962 Timestamp [UCT]: 2024-11-18 05:32:42 Age [y:d:h:m:s]: 01:051:15:40:18
Block: 1156183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295406 RingCT/type: yes/0
Extra: 01ec63d8ee6e8b54ec611722a0c5ec48f3146f5380f8bc40e0414134a6a49b6636021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f367965e89be74727f9a603b5a789c93a0f7882922216e43e35aa3de489d5139 0.600000000000 1641806 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": 1156193, "vin": [ { "gen": { "height": 1156183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f367965e89be74727f9a603b5a789c93a0f7882922216e43e35aa3de489d5139" } } ], "extra": [ 1, 236, 99, 216, 238, 110, 139, 84, 236, 97, 23, 34, 160, 197, 236, 72, 243, 20, 111, 83, 128, 248, 188, 64, 224, 65, 65, 52, 166, 164, 155, 102, 54, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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