Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d92c4db7c996e86c034539f1731a02ab74c65ce09f85c6eaf9e84320fa2fd1c

Tx prefix hash: 3f0d48754caf14818001834d8de93b4d981d2a2785257789199e1ac8811a48a9
Tx public key: eaf3bb969334f692d624b79b2fd2b132c5c500774ae825dc8ca53de44e326107
Timestamp: 1728041960 Timestamp [UCT]: 2024-10-04 11:39:20 Age [y:d:h:m:s]: 00:181:10:34:09
Block: 1124231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129454 RingCT/type: yes/0
Extra: 01eaf3bb969334f692d624b79b2fd2b132c5c500774ae825dc8ca53de44e32610702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e9b2718d98c0a4f8c9ed25b9d9f116036f760fbf5af9a50568184f489e58690 0.600000000000 1606830 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": 1124241, "vin": [ { "gen": { "height": 1124231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e9b2718d98c0a4f8c9ed25b9d9f116036f760fbf5af9a50568184f489e58690" } } ], "extra": [ 1, 234, 243, 187, 150, 147, 52, 246, 146, 214, 36, 183, 155, 47, 210, 177, 50, 197, 197, 0, 119, 74, 232, 37, 220, 140, 165, 61, 228, 78, 50, 97, 7, 2, 17, 0, 0, 0, 5, 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