Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40979dc37a2544b7ea8c10c756e9df664b088310dba697d4090dee2299cc6072

Tx prefix hash: 634cf9d6aabf666e9e9f1039141cd9de8ddd2c5255a292cf476a839b4c2be748
Tx public key: 379cc8c411200738276e84e12b390343080b3f922f1fb645fd21a1c8f4e57168
Timestamp: 1700363903 Timestamp [UCT]: 2023-11-19 03:18:23 Age [y:d:h:m:s]: 01:348:20:20:46
Block: 894762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508211 RingCT/type: yes/0
Extra: 01379cc8c411200738276e84e12b390343080b3f922f1fb645fd21a1c8f4e5716802110000000433af99f4000000000000000000

1 output(s) for total of 0.665705357000 dcy

stealth address amount amount idx
00: dfbc1df646af655aebd9d16b2100148ebf6d0251706e39e3d7d4622246226531 0.665705357000 1350969 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": 894772, "vin": [ { "gen": { "height": 894762 } } ], "vout": [ { "amount": 665705357, "target": { "key": "dfbc1df646af655aebd9d16b2100148ebf6d0251706e39e3d7d4622246226531" } } ], "extra": [ 1, 55, 156, 200, 196, 17, 32, 7, 56, 39, 110, 132, 225, 43, 57, 3, 67, 8, 11, 63, 146, 47, 31, 182, 69, 253, 33, 161, 200, 244, 229, 113, 104, 2, 17, 0, 0, 0, 4, 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