Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca4a790f383b2c27b6345379fc30b2684f33a4e7ba69637b673e787e990ca030

Tx prefix hash: 711cc39c383a8ecef402d904ed60f009c511baaefa7ab3a8047a5c5b799e3a91
Tx public key: 408a3c30d4c335e941bbe17f7f1c9f5f0640f5209f24219b02df79d4221eed08
Timestamp: 1715907794 Timestamp [UCT]: 2024-05-17 01:03:14 Age [y:d:h:m:s]: 00:238:23:06:47
Block: 1023635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171018 RingCT/type: yes/0
Extra: 01408a3c30d4c335e941bbe17f7f1c9f5f0640f5209f24219b02df79d4221eed0802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9a77e1ae70d560f11367165adfc35dd14454bc6ba3b87135ed68b415ae8f075 0.600000000000 1488758 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": 1023645, "vin": [ { "gen": { "height": 1023635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9a77e1ae70d560f11367165adfc35dd14454bc6ba3b87135ed68b415ae8f075" } } ], "extra": [ 1, 64, 138, 60, 48, 212, 195, 53, 233, 65, 187, 225, 127, 127, 28, 159, 95, 6, 64, 245, 32, 159, 36, 33, 155, 2, 223, 121, 212, 34, 30, 237, 8, 2, 17, 0, 0, 0, 2, 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