Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2745e74e3a0f9bb9db51e1909383ba0fa9d5906663a0de4d618484ce33221280

Tx prefix hash: ef0f0259e9a700cfb4f9fe056e5ba6a720036d091c9e66c46205b9591afe1d43
Tx public key: d49a11f9e95bc4398e8f3d3cb0bfa535a50353c4addeeb7edbcf548d7f1fe617
Timestamp: 1705615005 Timestamp [UCT]: 2024-01-18 21:56:45 Age [y:d:h:m:s]: 00:301:03:21:58
Block: 938279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215631 RingCT/type: yes/0
Extra: 01d49a11f9e95bc4398e8f3d3cb0bfa535a50353c4addeeb7edbcf548d7f1fe61702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de8f696455b695a761610db9605e13f610aaa5684ed6d86a3b38a9735b46fe37 0.600000000000 1396349 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": 938289, "vin": [ { "gen": { "height": 938279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de8f696455b695a761610db9605e13f610aaa5684ed6d86a3b38a9735b46fe37" } } ], "extra": [ 1, 212, 154, 17, 249, 233, 91, 196, 57, 142, 143, 61, 60, 176, 191, 165, 53, 165, 3, 83, 196, 173, 222, 235, 126, 219, 207, 84, 141, 127, 31, 230, 23, 2, 17, 0, 0, 0, 3, 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