Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0822aa171970b6b945bd4a60c1d939d5c0b26bf1d7c34388f0b4c5aca44ff8

Tx prefix hash: 31716f9404c184aa8b8ffad74f97bbf0c860b289be172c6452aca7cdb7529262
Tx public key: 26f69b994af1212e9473aaba542d14e9e5c656851d0c5ba296d58e8f84f0b7cd
Timestamp: 1711197639 Timestamp [UCT]: 2024-03-23 12:40:39 Age [y:d:h:m:s]: 01:053:09:07:39
Block: 984600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299130 RingCT/type: yes/0
Extra: 0126f69b994af1212e9473aaba542d14e9e5c656851d0c5ba296d58e8f84f0b7cd02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0bd5ce34dcafe749a40f786aa796bc7302f20cc37bafc7cdeb9682d370faab9 0.600000000000 1444771 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": 984610, "vin": [ { "gen": { "height": 984600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0bd5ce34dcafe749a40f786aa796bc7302f20cc37bafc7cdeb9682d370faab9" } } ], "extra": [ 1, 38, 246, 155, 153, 74, 241, 33, 46, 148, 115, 170, 186, 84, 45, 20, 233, 229, 198, 86, 133, 29, 12, 91, 162, 150, 213, 142, 143, 132, 240, 183, 205, 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