Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adda68d3456b6fd2af2cf1a28b9dc2cdac9a1e60c4cd123327cac0f807c6f286

Tx prefix hash: 4d343eb137e795f2a2480d72ecbf41e80f8ecbc443acd459302562b2001cec99
Tx public key: 4268af973232998816f6181c63fac9b4cf97c7246e72ed0cc4bd2fe7b77a370c
Timestamp: 1725932503 Timestamp [UCT]: 2024-09-10 01:41:43 Age [y:d:h:m:s]: 00:217:18:33:46
Block: 1106741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155483 RingCT/type: yes/0
Extra: 014268af973232998816f6181c63fac9b4cf97c7246e72ed0cc4bd2fe7b77a370c021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5bdf452177a9b36554b2d1e3d4ea2beba5e5d3e73a5bf0b31d46f731a5f09f9 0.600000000000 1584342 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": 1106751, "vin": [ { "gen": { "height": 1106741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5bdf452177a9b36554b2d1e3d4ea2beba5e5d3e73a5bf0b31d46f731a5f09f9" } } ], "extra": [ 1, 66, 104, 175, 151, 50, 50, 153, 136, 22, 246, 24, 28, 99, 250, 201, 180, 207, 151, 199, 36, 110, 114, 237, 12, 196, 189, 47, 231, 183, 122, 55, 12, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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