Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5186fc44db91b7ed0fc60c1ee839c69213ca86c036afb2472a75d44dcedc87f6

Tx prefix hash: 9beee3d4e10d8b6e3c185c9dcfb75925de87b6f6b780ce2a98ddabf0ad2b15fd
Tx public key: 764a1453cc1223d22b835200abdae5254714fca1c715447bb5e8cd4d15c54f2e
Timestamp: 1715134601 Timestamp [UCT]: 2024-05-08 02:16:41 Age [y:d:h:m:s]: 00:232:14:26:20
Block: 1017219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166482 RingCT/type: yes/0
Extra: 01764a1453cc1223d22b835200abdae5254714fca1c715447bb5e8cd4d15c54f2e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd058ab5aeeb97c612f3d611e881f96e1a4fc55ebcb437887aeee4fa0191e0a5 0.600000000000 1480988 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": 1017229, "vin": [ { "gen": { "height": 1017219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd058ab5aeeb97c612f3d611e881f96e1a4fc55ebcb437887aeee4fa0191e0a5" } } ], "extra": [ 1, 118, 74, 20, 83, 204, 18, 35, 210, 43, 131, 82, 0, 171, 218, 229, 37, 71, 20, 252, 161, 199, 21, 68, 123, 181, 232, 205, 77, 21, 197, 79, 46, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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