Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32769465a038382152cf623d05758b44f37ab0ef0f48910ab533f0669d975d1c

Tx prefix hash: f20c91d1f14bc6fefb9ffef05912d30780a78243b2e181f4ba0c9b8409429de1
Tx public key: 5ce564c0f0661e7519b0997e22ea770f9b0a510304aaa7705389f2a8458dd838
Timestamp: 1699215346 Timestamp [UCT]: 2023-11-05 20:15:46 Age [y:d:h:m:s]: 01:210:04:49:52
Block: 885235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411475 RingCT/type: yes/0
Extra: 015ce564c0f0661e7519b0997e22ea770f9b0a510304aaa7705389f2a8458dd83802110000000233af99f4000000000000000000

1 output(s) for total of 0.715894410000 dcy

stealth address amount amount idx
00: 962f3a408d1b5a5a1d3827d54014eb7d49521cac4fb63cd1b4b530c987a1379d 0.715894410000 1340998 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": 885245, "vin": [ { "gen": { "height": 885235 } } ], "vout": [ { "amount": 715894410, "target": { "key": "962f3a408d1b5a5a1d3827d54014eb7d49521cac4fb63cd1b4b530c987a1379d" } } ], "extra": [ 1, 92, 229, 100, 192, 240, 102, 30, 117, 25, 176, 153, 126, 34, 234, 119, 15, 155, 10, 81, 3, 4, 170, 167, 112, 83, 137, 242, 168, 69, 141, 216, 56, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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