Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbdc4bdf80e3b367ccf7a86cf856f74e9fa10a993ae6925e26ae9b8791b7d779

Tx prefix hash: 4b6face4231aef827f630e76bc89317ecb70de3e624ab8be5f24449907589ce7
Tx public key: f694a2599668cd6c3b4568dd641d9d0d9967bb984929e5161a85a06deb8dbec6
Timestamp: 1707206944 Timestamp [UCT]: 2024-02-06 08:09:04 Age [y:d:h:m:s]: 01:070:01:38:10
Block: 951483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311145 RingCT/type: yes/0
Extra: 01f694a2599668cd6c3b4568dd641d9d0d9967bb984929e5161a85a06deb8dbec6021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e79ea589ca6c16b1697153e33b34396fdab8e9793a154eab7bae9d542a3e4159 0.600000000000 1410253 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": 951493, "vin": [ { "gen": { "height": 951483 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e79ea589ca6c16b1697153e33b34396fdab8e9793a154eab7bae9d542a3e4159" } } ], "extra": [ 1, 246, 148, 162, 89, 150, 104, 205, 108, 59, 69, 104, 221, 100, 29, 157, 13, 153, 103, 187, 152, 73, 41, 229, 22, 26, 133, 160, 109, 235, 141, 190, 198, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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