Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c4b31452e2fccf2c7699b96c27ae4240fee520537e415943b8b680434f04873

Tx prefix hash: b50a36b176460bc12e4bf552fd6e9772e0be379fb6ceec6e44569a9021a446cd
Tx public key: 5e3115df048a6d844dad2ecf1602ea48d79d3c58f4b5b0e547fd8b4c249f0b33
Timestamp: 1674060371 Timestamp [UCT]: 2023-01-18 16:46:11 Age [y:d:h:m:s]: 02:038:01:14:14
Block: 677553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548829 RingCT/type: yes/0
Extra: 015e3115df048a6d844dad2ecf1602ea48d79d3c58f4b5b0e547fd8b4c249f0b330211000000038b7b6602000000000000000000

1 output(s) for total of 3.491287323000 dcy

stealth address amount amount idx
00: 4a3a982bd823e03de75aafa92a2dce047ce13d7b7974e703b11bf8404d94b116 3.491287323000 1119336 of 0

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": 677563, "vin": [ { "gen": { "height": 677553 } } ], "vout": [ { "amount": 3491287323, "target": { "key": "4a3a982bd823e03de75aafa92a2dce047ce13d7b7974e703b11bf8404d94b116" } } ], "extra": [ 1, 94, 49, 21, 223, 4, 138, 109, 132, 77, 173, 46, 207, 22, 2, 234, 72, 215, 157, 60, 88, 244, 181, 176, 229, 71, 253, 139, 76, 36, 159, 11, 51, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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