Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52bfd67bb1ab3d01ccf5e40d50d5af31d28aba7f9bd543703b830851a9b3750a

Tx prefix hash: 7385ff95d74d3d1eb7712a0d4fc41854c308b143da07338efbfac1301720c5f0
Tx public key: 944f2b27fab85cc16dbfd8d5975b25b3c649e78f4e9642c810182b90e28b5e18
Timestamp: 1715607782 Timestamp [UCT]: 2024-05-13 13:43:02 Age [y:d:h:m:s]: 00:336:00:29:48
Block: 1021163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240167 RingCT/type: yes/0
Extra: 01944f2b27fab85cc16dbfd8d5975b25b3c649e78f4e9642c810182b90e28b5e18021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 387d7e8d1737ac936b0a2af181528b91b653c138315c33129ac33d3ff3c48d01 0.600000000000 1485394 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": 1021173, "vin": [ { "gen": { "height": 1021163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "387d7e8d1737ac936b0a2af181528b91b653c138315c33129ac33d3ff3c48d01" } } ], "extra": [ 1, 148, 79, 43, 39, 250, 184, 92, 193, 109, 191, 216, 213, 151, 91, 37, 179, 198, 73, 231, 143, 78, 150, 66, 200, 16, 24, 43, 144, 226, 139, 94, 24, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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