Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a262c2186438f025e93d45100f77c5a6f75f0838715b8356b1fe3a91e86d32

Tx prefix hash: 78cc81c990f39b5b1833312c1da7c8a8e8343c6f64ed701a4ea59dcd59570514
Tx public key: b03130be6a2c48c6d685aafd0c70a75cf3a2094fd986d89be17b3abf0d6eb866
Timestamp: 1712501039 Timestamp [UCT]: 2024-04-07 14:43:59 Age [y:d:h:m:s]: 00:217:19:23:22
Block: 995357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155942 RingCT/type: yes/0
Extra: 01b03130be6a2c48c6d685aafd0c70a75cf3a2094fd986d89be17b3abf0d6eb8660211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4037c191f6bec6918ce0885f7c7ba318342e81c39b0064bb1f11b645459a9705 0.600000000000 1455765 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": 995367, "vin": [ { "gen": { "height": 995357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4037c191f6bec6918ce0885f7c7ba318342e81c39b0064bb1f11b645459a9705" } } ], "extra": [ 1, 176, 49, 48, 190, 106, 44, 72, 198, 214, 133, 170, 253, 12, 112, 167, 92, 243, 162, 9, 79, 217, 134, 216, 155, 225, 123, 58, 191, 13, 110, 184, 102, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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